Diag Summary (GameOS)

It describes the procedure to be taken when each test executed by GameOS LSI Diag hangs up and when an error occurs.

GPU Memory test

It is a high-speed GDDR Memory Test using GPU.
There are two main types to check: Pattern match and Address match.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

0xFE000801 (Pattern Verify Test Failed (##))

Data does not match in GDDR fixed patterm match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE000802 (Address Verify Test Failed (##))

Data does not match in GDDR address match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE000803 (Random Verify Test Failed (##))

Data does not match in GDDR random pattern match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

gdsdiag

It is a test of GDS (built-in memory) in GPU.

0xFE000311 (GDS Test Error Occurred (##))

An error occurred in the MSoC GC GDS read / write test.

Procedure when an error occurs in this Diag

  1.  If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

ldsdiag

It is a test of LDS (built-in memory) in GPU.

0xFE000301 (LDS Test Error Occurred (##))

An error occurred in the MSoC GC LDS read / write test.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

gpu integrated test

The following GPU Test runs on a single process.

  1. streambench

  2. simplet-3d2

  3. simplet-tess-gs

  4. GPU 4k Test

  5. HMD Test

  6. basic sample

  7. bambitree3

streambench (Garlic)

It is a BUS high load test that reads / writes several patterns of data from GPU to GDDR.

0xFE100001 (MSoC Garlic Stress Test Error Occured (##))

An error occurred during high load transfer from MSoC GPU to GDDR via Garlic Bus.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE100002 (MSoC Garlic Stress Test Performance Error Occured (##))

Performance Error occurred during high load transfer from MSoC GPU to GDDR via Garlic Bus.

Procedure when an error occurs in this Diag

  1. Make sure that no EDC Error has occurred.
    Refer to 0xF0050100 for the presence or absence of EDC Error.

  2. If an EDC Error occurs, the transfer speed is slowing down due to the EDC Error.

streambench (Onion)

0xFE100011 (MSoC Onion Stress Test Error Occured (##))

An error occurred during high load transfer from MSoC GPU to GDDR via Onion Bus.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE100012 (MSoC Onion Stress Test Performance Error Occured (##))

Performance Error occurred during high load transfer from MSoC GPU to GDDR via Onion Bus.

Procedure when an error occurs in this Diag

  1. Make sure that no EDC Error has occurred.
    Refer to 0xF0050100 for the presence or absence of EDC Error.

  2. If an EDC Error occurs, the transfer speed is slowing down due to the EDC Error.

  3. If there is no problem with the above, it is suspected that the Main SoC is defective.

streambench (Onion Plus)

0xFE100031 (MSoC Onion Plus Stress Test Error Occured (##))

An error occurred during high load transfer from MSoC GPU to GDDR via Onion Plus Bus.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE100032 (MSoC Onion Plus Stress Test Performance Error Occured (##))

Performance Error occurred during high load transfer from MSoC GPU to GDDR via Onion Plus Bus.

Procedure when an error occurs in this Diag

  1. Make sure that no EDC Error has occurred.
    Refer to 0xF0050100 for the presence or absence of EDC Error.

  2. If an EDC Error occurs, the transfer speed is slowing down due to the EDC Error.

  3. If there is no problem with the above, it is suspected that the Main SoC is defective.

simplet-3d2

Test using all Shader LS, HS, ES, GS, VS, PS of Graphics.
It also use Tessellation and Color Blending.
Check if the CRC of the GPU calculation result matches the expected value.

0xFE000701 (Graphics simplet-3d2 CRC NG (##) )

The CRC of the calculation result using GPU Graphics shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

simplet-tess-gs

It is a test that mainly confirms Compute Shader using all Shader LS, HS, ES, GS, VS, PS of Graphics.
It also use Tessellation and Color Blending.
Check if the CRC of the GPU calculation result matches the expected value.

0xFE000711 (Compute Result Failed (##) )

The result of calculation using GPU Compute shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE000712 (Graphics CRC NG (##) )

The CRC of the calculation result using GPU Graphics shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

GPU 4k test

This is a Test that checks Graphics' HW for 4K, Checker Bard, PS Invoke, Gradient Adjust, and Object ID.
Check if the CRC of the GPU calculation result matches the expected value.

0xFE000901 (Graphics 4k Test CRC NG (##) )

The CRC of the calculation result using HW for GPU 4k does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

HMD test

It is a test to check HW, Scale Resolution by Screen Location for HMD of GPU.  Check if the CRC of the GPU calculation result matches the expected value.

0xFE000A01 (HMD Test CRC NG (##) )

The CRC of the calculation result using the HW for GPU HMD does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

basic sample

Test using VS and PS of Graphics.
It also use Dispatch Draw, Instancing, Depth Buffer and Index Offset.
Check if the CRC of the GPU calculation result matches the expected value.

0xFE000B01 (Graphics Basic Sample Test CRC NG (##) )

The CRC of the calculation result using GPU shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

GPU Native Mode Tests

AGC Basic Tessellation Test

This is a test that performs drawing using Graphics LS, HS, DS, PS and Compute operation at the same time in Native mode (gen2).
Check if the Graphics operation result (CRC) and Compute operation result match the expected value.

0xFE001011 (Graphics CRC Verify failed (##) )

The CRC of the calculation result using GPU Graphics shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001012 (Compute Verify failed (##) )

The result of calculation using GPU Compute shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Native Stream Test

BUS high load test that reads / writes several patterns of data from GPU operating in Native mode (gen2) to GDDR.

0xFE001031 (Verify Error Occured (##))

An error occurred during high load transfer from MSoC GPU to GDDR.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE001032 (Performance Error Occurred (##))

Performance Error occurred during high load transfer from MSoC GPU to GDDR.

Procedure when an error occurs in this Diag

  1. Make sure that no EDC Error has occurred.
    Refer to 0xF0050100 for the presence or absence of EDC Error.

  2. If an EDC Error occurs, the transfer speed is slowing down due to the EDC Error.

  3. If there is no problem with the above, it is suspected that the Main SoC is defective.

Native Gpu Memory Test

It is a high-speed GDDR Memory Test using GPU that operates in Native mode (gen2).
There are two main types to check: Pattern match and Address match.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

0xFE001041 (Pattern Verify Test Failed (##))

Data does not match in GDDR fixed patterm match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE001042 (Address Verify Test Failed (##))

Data does not match in GDDR address match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE001043 (Invert Address Verify Test Failed (##))

Data does not match in GDDR invert address match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xFE001044 (Random Verify Test Failed (##))

Data does not match in GDDR random pattern match Memory Test.
GDDR is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

Native Mem PState Test

Memory Test, Clock confirmation, and image output system operation are performed in the power saving state with MemCLK dropped.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

Please refer to the following for the error code and contents.

  1. Native Gpu Memory Test

  2. Flava Diag

Basic Ray Tracing Test

This is a test that draws using the Ray Tracing function of Graphics in Native mode (gen2).
Check if the Graphics operation result (CRC) matches the expected value.

0xFE001051 (CRC Verify failed (##) )

Graphics calculation result CRC using GPU Ray Tracing function does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

RT FSR Combined Test

This is a test that draws using the Ray Tracing / FSR function of Graphics in Native mode (gen2).
Check if the Graphics operation result (CRC) matches the expected value.

0xFE001061 (CRC Verify failed (##) )

Graphics calculation result CRC using GPU Ray Tracing / FSR function running on GFX ring does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001062 (HP3D CRC Verify failed (##) )

Graphics calculation result CRC using GPU Ray Tracing / FSR function running on HP3D ring does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001063 (HP3D Graphics Shader might be hang (##) )

The Graphics Shader of the GPU running on the HP3D ring has not completed its operation after the specified time.
GPU is hang up.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

NGG SR FSR Combined Test

This is a test that draws using the NGG / Stereo Rendering / FSR function of Graphics in Native mode (gen2).
Check if the Graphics operation result (CRC) matches the expected value.

0xFE001071 (CRC Verify failed (##) )

Graphics calculation result CRC using NGG / Stereo Rendering / FSR function does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Metadata POPS Test

It is a test that draws using the functions such as Metadata / POPS / Blending / Dispatch Tunneling of Graphics in Native mode (gen2).
Check if the result of the Graphics operation matches the expected value.

0xFE001081 (Hash mismatch (##) )

Murmur3 Hash of Graphics calculation result using functions such as Metadata / POPS / Blending / Dispatch Tunneling does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001082 (CRC Verify failed (##) )

Graphics calculation result CRC using functions such as Metadata / POPS / Blending / Dispatch Tunneling does not match the expected value。
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Async Pipe Bitonic Sort Test

It is a test that performs Bitonic Sort operation with Compute (Async Pipe) in Native mode (gen2).
Make sure the Sort result is correct.

0xFE001091 (Pipe: X, Queue: X, Loop: X, Sort X failed)

The Bitonic Sort result calculated by Compute (Async Pipe) is incorrect.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

White Oak

It is a test that draws using the GPU Ray Tracing function in Native mode (gen2).
Check if the Graphics operation result (CRC) matches the expected value.

0xFE001101 (Shader might be hang (##))

Calculation using GPU shader is not completed within the specified time.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001102 (CRC Verify failed (##) )

The calculation result CRC using the GPU Ray Tracing function does not match the expected value.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Agc Metadata Compression

A test that draws using the Delta Color Compression (DCC) supported by the GPU.
This is a test to check if the Graphics operation result (CRC) matches the expected value, and if the CRC of the processing result of the Main SoC DCN Block and the CRC of the HDMI transmitter match the expected value.
Outputs 1080p images.

0xFE001201 (CRC Verify Test Failed (##))

The CRC of the calculation result using GPU Graphics shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001202 (Link status error)

Link between Main Soc and HDMI transmitter is abnormal

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between HDMI transmitter and Main SoC

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

0xFE001203 (MSoC CRCs are wrong)

The CRC of the Main SoC does not match the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001204 (MSoC-Flava CRCs are not same)

The CRC of the Main SoC and HDMI transmitter do not match.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

RT FSR Combined Lo Test

This is a test that draws using the Ray Tracing / FSR function of Graphics in Native mode (gen2).
Check if the Graphics operation result (CRC) matches the expected value.
This is an improved version of the Rt FSR Combined Test.

0xFE001301 (Graphics Shader might be hang (##))

Graphics calculation using GPU Ray Tracing / FSR function is not completed within the specified time.
MSoC or Memory is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Mode Transition Test

Perform Clock confirmation, MemoryTest, Gfx / Compute combined operation test in the power saving state (Navigation Active0 / Active1 / Inactive) with CCLK, GFXCLK, and MemCLK dropped.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

Please refer to the following for the error code and contents.

  1. Native Gpu Memory Test

  2. AGC Basic Tessellation Test

CPU Tests

CPU Memory Test

It is a test that inspects GDDR from the CPU.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

0xFD000005 (CPU Memory Pattern Test Verify error occurred.)

A data mismatch was detected in the Fixed Pattern Memory Test to GDDR.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFD000006 (CPU Memory Address Test Verify error occurred.)

A data mismatch was detected in the Address Pattern Memory Test to GDDR.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFD000007 (CPU Memory Random Test Verify error occurred.)

A data mismatch was detected in the Random Pattern Memory Test to GDDR.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

UNB Stress Test

Concurrent 10 MiB size memory copies individually on each CPU Core for separate memory areas.
After copying, perform data check.
If this test fails, it may be GDDR, MainSoC, or a mounting failure.

0xFD000014 (Verify error occurred.)

A data mismatch has been detected.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test, Cpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFD000015 (AvgBW threshold error occurred.)

A data transfer bandwidth not reached error has been detected.

Procedure when an error occurs in this Diag

  1.  If the Native Gpu Memory Test, Cpu Memory Test passes, it is suspected that the Main SoC is defective.

Flava Diag

This is a test to check if the CRC of the processing result of Main SoC DCN Block and the CRC of HDMI transmitter match the expected value.
Outputs 1080p images.

0xFE500101 (Could not get CRC information from Flava)

Communication between Main SoC DCN and HDMI transmitter was not possible.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

0xFE500102 (Link status error)

The link between the Main SoC and HDMI transmitter is abnormal.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

0xFE500103 (MSoC CRCs are wrong)

The CRC of the Main SoC does not match the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE500104 (MSoC-Flava CRCs are not same)

The CRC of the Main SoC and HDMI transmitter do not match.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

DCN Diag

This is a test to check if the CRC of the processing result of Main SoC DCN Block and the CRC of HDMI transmitter match the expected value.
Outputs a blended image of 4k and 1080p images.

There are two types of 4k Test, 60p and 120p. In the case of 60p, the Error Code is the same as Flava Diag.
Please refer to the Error Code of Flava Diag.
In the case of 4k120p, the following Error Code will be displayed.

0xFE500111 (Could not get CRC information from Flava)

Communication between Main SoC DCN and HDMI transmitter was not possible.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

0xFE500112 (Link status error)

The link between the Main SoC and HDMI transmitter is abnormal.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

0xFE500113 (MSoC CRCs are wrong)

The CRC of the Main SoC does not match the expected value.。

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE500114 (MSoC-Flava CRCs are not same)

The CRC of the Main SoC and HDMI transmitter do not match.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

  2. Procedure if Main SoC is suspicious

    1. Check the DisplayPort signal between the HDMI transmitter and the Main SoC.

    2. If there is no problem with the mounting, HDMI transmitter is suspected.

    3. If the same error occurs even after replacing the HDMI transmitter, it is suspected to be Main SoC.

Complex Tests

Matmult Bambitree

It is a test that operates the CPU and GPU with a high load and confirms whether the calculation result matches the expected value.

0xFE200001 (MSoC GC Stress Test Error Occurred.)

GPU data check error has occurred.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Matmult Bambitree3

It is a test that operates the CPU and GPU with a high load and confirms whether the calculation result matches the expected value.

0xFD000024 (matmult verify error occurred.)

The CPU calculation result is different from the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test ,  Cpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE000F01 (Bambitree3 Test CRC NG (##) )

The CRC of the calculation result using GPU shader does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE000F02 (Bambitree3 Shader might be hang (##) )

Calculation using GPU shader is not completed within the specified time.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Native Power Test

This is a test to check if the calculation result matches the expected value by operating the CPU and GPU with high load in Native mode.

0xFE001021 (CPU Verify failed)

The CPU high load calculation result does not match the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test,  Cpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001022 (Compute Verify failed)

GPU Compute high load calculation result does not match the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xFE001023 (Graphics Verify failed)

GPU Graphics High load calculation result does not match the expected value.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Clock Check

0xFE600002 (<clock name> Clock margin failed)

It is detected when the frequency of <clock name> is different from the expected value in the Clock Check immediately after starting Diag or after Mode Switch.

Procedure when an error occurs in this Diag

  1. Retest 3 times and check the error log

  2. If it reoccurs, it is suspected to be defective in the order of Clock Source input to Main SoC, HDMI transmitter.

Common

0xF0050209 (Shader might be hang (##))

The operation of the GPU Shader has not been completed even after the specified time.
GPU is hang up.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xF005020A (Job might be hang (##))

Diag has not completed its operation after the specified time.
Diag is hang up.
The power supply system, Memory, and Main SoC are defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xF005020B (cpDMA might be hang (##))

The operation of cpDMA transfer has not been completed even after the specified time.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xF005020E (MD5 mismatch (FILE))

The MD5 Digest value in FILE does not match the expected value.
The USB Mass Storage may be degraded or the FILE in Mass Storage may be corrupted.

Procedure when an error occurs in this Diag

  1. Reformat the USB Mass Storage.

  2. If it is frequent, it is suspected that the USB Mass Storage itself is destroyed.

0xF0050213 (Graphics Shader might be hang (##))

The GPU Graphics Shader has not completed its operation after the specified time.
GPU is hang up.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xF0050214 (Compute Shader might be hang (##))

The GPU Compute Shader has not completed its operation after the specified time.
GPU is hang up.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

0xF0050215 (Memory Verify Failed)

The value of Memory allocated by lsi_diag main does not match the expected value.
Memory or Main SoC is suspected of being defective.

Procedure when an error occurs in this Diag

  1. See How to check decoded GDDR’s addresses

0xF0050218 (HP3D crashed)

HP3D Crash is occurring.

Procedure when an error occurs in this Diag

. Retest 3 times and collect the error log. If it reoccurs, it is suspected that the Main SoC is defective.

0xF0050219 (Target condition failed)

The state of Target is not as expected.

Procedure when an error occurs in this Diag


. Make sure that Target is not running in Safe Mode.

0xF0050100 (Too many WEDC/REDC is detected (##))

EDC Error is occurring in the communication between MainSoC and GDDR6
Whether or not EDC Error occurs for each umc and ch is output as a log as shown below.

[DEBUG]:  61.0619 <umc_show_pmc_ctr> EDC Error Information (error check mode)
[DEBUG]:  61.0653 <umc_show_pmc_ctr> Umc0Ch0: (WEDC / Write) = (    0 / 1272037980) (  0.00 ppm)
[DEBUG]:  61.0695 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001687913) (  0.00 ppm)
[DEBUG]:  61.0738 <umc_show_pmc_ctr> Umc0Ch1: (WEDC / Write) = (    0 / 1273401823) (  0.00 ppm)
[DEBUG]:  61.0780 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001518195) (  0.00 ppm)
[DEBUG]:  61.0823 <umc_show_pmc_ctr> Umc1Ch0: (WEDC / Write) = (    0 / 1272183850) (  0.00 ppm)
[DEBUG]:  61.0865 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001776747) (  0.00 ppm)
[DEBUG]:  61.0907 <umc_show_pmc_ctr> Umc1Ch1: (WEDC / Write) = (    0 / 1380322785) (  0.00 ppm)
[DEBUG]:  61.0950 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001529395) (  0.00 ppm)
[DEBUG]:  61.0992 <umc_show_pmc_ctr> Umc2Ch0: (WEDC / Write) = (    0 / 1272600517) (  0.00 ppm)
[DEBUG]:  61.1035 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002097655) (  0.00 ppm)
[DEBUG]:  61.1077 <umc_show_pmc_ctr> Umc2Ch1: (WEDC / Write) = (    0 / 1281968013) (  0.00 ppm)
[DEBUG]:  61.1119 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001936173) (  0.00 ppm)
[DEBUG]:  61.1161 <umc_show_pmc_ctr> Umc3Ch0: (WEDC / Write) = (    0 / 1273917515) (  0.00 ppm)
[DEBUG]:  61.1204 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002131266) (  0.00 ppm)
[DEBUG]:  61.1246 <umc_show_pmc_ctr> Umc3Ch1: (WEDC / Write) = (    0 / 1348617577) (  0.00 ppm)
[DEBUG]:  61.1289 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002372138) (  0.00 ppm)
[DEBUG]:  61.1331 <umc_show_pmc_ctr> Umc4Ch0: (WEDC / Write) = (    0 / 1276082950) (  0.00 ppm)
[DEBUG]:  61.1374 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001965054) (  0.00 ppm)
[DEBUG]:  61.1416 <umc_show_pmc_ctr> Umc4Ch1: (WEDC / Write) = (    0 / 1274336597) (  0.00 ppm)
[DEBUG]:  61.1458 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002053104) (  0.00 ppm)
[DEBUG]:  61.1500 <umc_show_pmc_ctr> Umc5Ch0: (WEDC / Write) = (    0 / 1272696018) (  0.00 ppm)
[DEBUG]:  61.1543 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001991602) (  0.00 ppm)
[DEBUG]:  61.1585 <umc_show_pmc_ctr> Umc5Ch1: (WEDC / Write) = (    0 / 1271145477) (  0.00 ppm)
[DEBUG]:  61.1628 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001796559) (  0.00 ppm)
[DEBUG]:  61.1670 <umc_show_pmc_ctr> Umc6Ch0: (WEDC / Write) = (    1 / 1272203876) (  0.00 ppm)
[DEBUG]:  61.1712 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001984890) (  0.00 ppm)
[DEBUG]:  61.1803 <umc_show_pmc_ctr> Umc6Ch1: (WEDC / Write) = (    0 / 1272820601) (  0.00 ppm)
[DEBUG]:  61.1845 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002140591) (  0.00 ppm)
[DEBUG]:  61.1889 <umc_show_pmc_ctr> Umc7Ch0: (WEDC / Write) = (    0 / 1274724371) (  0.00 ppm)
[DEBUG]:  61.1931 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1001933864) (  0.00 ppm)
[DEBUG]:  61.1973 <umc_show_pmc_ctr> Umc7Ch1: (WEDC / Write) = (    0 / 1411178851) (  0.00 ppm)
[DEBUG]:  61.2016 <umc_show_pmc_ctr>          (REDC / Read)  = (    0 / 1002106159) (  0.00 ppm)

Procedure when an error occurs in this Diag

  1. Check the mounting status of MainSoC and GDDR6

  2. If the Native Gpu Memory Test passes, it is suspected that the Main SoC is defective.

Tips

How to check decoded GDDR’s addresses

When Verify Error is detected by memorytest etc.
GDDR Address Decode information as shown in the example below is output to Log.

[ERROR]: umc.4 ch.0 phy.E
[ERROR]: expect 0x00000000 actual 0x00000004 numErrorBits 1

  1. Perform the test multiple times and collect the error logs for multiple times.

  2. If an error is detected with the same umc, ch every time, there is a high possibility that GDDR is defective. If the umc, ch is different, it is suspected that the Main Soc is defective.

SCF NAND/SSD test

This is SCF and NAND diag.
See SCF NAND/SSD test.